-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Write a custom lint rule to disable use of logrus package #6357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## main #6357 +/- ##
==========================================
- Coverage 70.48% 70.42% -0.07%
==========================================
Files 515 517 +2
Lines 23150 23265 +115
==========================================
+ Hits 16317 16384 +67
- Misses 5776 5822 +46
- Partials 1057 1059 +2
Continue to review full report at Codecov.
|
53d6a2f
to
7e6d540
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rm -rf hack/tools/vendor
too
9abb1f6
to
d56ce77
Compare
d56ce77
to
5aadccc
Compare
Shd merge after #6531
As part of @MarlonGamez's proposed solution to wire up logrus debug and info level messages correctly, I am writing a custom lint rule to fail is
Currently due to golang/go#19569 and golangci/golangci-lint#1276, there is no way to run private custom linter as part of
golangco-lint
.Hence the proposed solution is to run it as a binary in existing
hack/golangci-lint.sh
.TODO
hack/golangci-lint.sh
by defaultSample output